Expanding list of CODEOWNERS for registry.json to include Foundry developers.#9164
Conversation
|
Azure Pipelines: 22 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
|
Azure Pipelines: 22 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
There was a problem hiding this comment.
Pull request overview
Expands registry ownership so Foundry developers can approve routine extension publishing updates.
Changes:
- Adds Foundry developers as code owners for
registry.json. - Retains core-review enforcement for complex registry changes.
Show a summary per file
| File | Description |
|---|---|
.github/CODEOWNERS |
Expands ownership of the extension registry. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Medium
📋 Prioritization NoteThanks for the contribution! The linked issue isn't in the current milestone yet. |
|
/check-enforcer evaluate |
|
/check-enforcer override |
|
CC: @XiaofuHuang @achauhan-scc @anchenyi @glharper @huimiu @hund030 @kingernupur @saanikaguptamicrosoft @therealjohn @trangevi @trrwilson Okay NOW you can approve extension release PRs, sorry about that false alarm earlier. :) Check the PR message for instructions, but it should be pretty much like any ole' PR for most situations. |
Welcome new developers to registry.json :) (once this PR merges!)
The basics of how this'll work for you, with regards to registry PRs:
If it's just a simple registry update (new version for an existing extension, no provider or capability updates) then you, or anyone else in CODEOWNERS can just approve and merge the PR.
If it's a complex one (ie, any of those things change), you'll see this PR workflow fail:
If you click it (link) it'll tell you the specific item that's requires approval. So then:
Fixes #8997